Methods and apparatus for dynamic user authentication using customizable context-dependent interaction across multiple verification objects

ABSTRACT

An authentication framework is provided which enables dynamic user authentication that combines multiple authentication objects using a shared context and that permits customizable interaction design to suit varying user preferences and transaction/application requirements. Such a framework provides a high degree of flexibility, accuracy, convenience and robustness. In one illustrative aspect of the invention, an automated technique for user authentication comprises the following steps/operations. First, user input is obtained. At least a portion of the user input is associated with two or more verification objects. Then, the user is verified based on the two or more verification objects in accordance with at least one verification policy operating on a context shared across the two or more verification objects. The user authentication technique of the invention may preferably be implemented in a flexible, distributed architecture comprising at least one client device coupled to at least one verification server. The client device and the verification server may operate together to perform the user authentication techniques of the invention.

FIELD OF THE INVENTION

[0001] The present invention relates to authentication techniques and, more particularly, to techniques for providing dynamic user authentication using customizable context-dependent interaction across multiple verification objects.

BACKGROUND OF THE INVENTION

[0002] Authenticating the identity claim of a user is an important step in ensuring the security of systems, networks, services and facilities, both for physical and for logical access. Existing user authentication is often performed on the basis of a user's knowledge of a single verification object, e.g., a password or a personal identification number (PIN). Existing user authentication may also be performed on the basis of possession of a single verification object, e.g., a key or a card. Other existing authentication techniques include the use of a single biometric feature as the verification object, e.g., a fingerprint, a voiceprint, an iris scan or a face scan.

[0003] Verification is typically done by comparing the verification object obtained from the user at the time of attempted access to previously stored objects. Thus, in the case of a fingerprint, if the fingerprint obtained from the user at the time of attempted access matches a prestored fingerprint (presumably taken from the user at some earlier time), then access is granted. If no match is found, then access is denied.

[0004] However, these existing authentication techniques have many drawbacks. For example, keys or passwords may be stolen or biometric features may be compromised, e.g., using false fingerprints.

[0005] More recent techniques attempt to use more than one biometric recognition technique, such as face and voice print recognition. However, such techniques typically acquire and analyze each biometric feature sequentially and independently and merely combine the final outputs in a predetermined static manner, and thus do not utilize any interaction between biometrics.

[0006] Further, existing authentication techniques fail to provide enough flexibility to address various user-specific, transaction-specific or application-specific constraints or requirements. For example, a user-specific constraint may be that a user with a cut on his finger may not be able to use a fingerprint recognition system. A transaction-specific constraint may be that a million dollar transaction should require a higher degree of authentication as opposed to a ten dollar transaction. An application-specific constraint may be that security questions based on a banking application may not be suitable for a travel application. Existing authentication approaches are just not flexible enough to handle these types of constraints or requirements.

[0007] Accordingly, given the growing interest in security and authentication and the deficiencies of existing authentication systems, there is a clear need for an improved authentication framework that provides a high degree of flexibility, accuracy, convenience and/or robustness.

Summary of the Invention

[0008] The present invention provides an improved authentication framework affording greater flexibility, accuracy, convenience and robustness as compared to existing authentication frameworks. This is accomplished, for example, by enabling dynamic user authentication that combines multiple authentication objects using a shared context and that permits customizable interaction design to suit varying user preferences and transaction/application requirements. Such a framework advantageously provides a high degree of flexibility, accuracy, convenience and robustness.

[0009] In one aspect of the invention, an automated technique for user authentication comprises the following steps/operations. First, user input is obtained. At least a portion of the user input is associated with two or more verification objects. Then, the user is verified based on the two or more verification objects in accordance with at least one verification policy operating on a context shared across the two or more verification objects.

[0010] The user verification step/operation is preferably performed in accordance with two or more verification engines which are respectively responsive to the two or more verification objects. The two or more verification engines may respectively compare the two or more verification objects to at least one user model. The user model may be previously generated based on data obtained in accordance with a user enrollment session.

[0011] Further, the context that is shared across the two or more verification objects may comprise one or more variables associated with the user verification step/operation. For example, the context variables may represent one or more of: (i) a user name; (ii) a current state in the at least one verification policy; (iii) a history pertaining to the two or more verification objects; (iv) application-specific requirements; (v) user-specific requirements; and (vi) physical or logical variables. Still further, the two or more verification objects may represent object types that may be used to verify identity of the user, knowledge of the user, and possessions of the user.

[0012] In another aspect of the invention, the user authentication technique is customizable in that the technique may comprise the steps/operations of adding, modifying and/or deleting a verification policy, a verification object type, a user model, and/or a variable associated with the context. These tasks may be accomplished in an administrative session.

[0013] In yet another aspect of the invention, the user authentication technique is implemented in a flexible, distributed architecture comprising at least one client device coupled to at least one verification server. The client device and the verification server may operate together to perform the inventive user authentication techniques described herein.

[0014] A communication interface between the client device and the verification server may be implemented in accordance with Extensible Markup Language (XML). Such a communication interface between the client device and the verification server may support a verification session, an enrollment session and/or an administrative session.

[0015] In a further aspect of the invention, the user authentication technique comprises the use of at least one verification policy and verification means operative to verify a user in accordance with the at least one verification policy, wherein the at least one verification policy is implementable in accordance with the verification means as a state machine. It is to be understood that verification means, as referred to herein, may be realized in a number of implementations, e.g., a verification module which can be implemented in hardware, software, and/or combinations thereof.

[0016] In yet another aspect of the invention, the user authentication technique comprises the use of at least one verification object and verification means operative to verify a user in accordance with the at least one verification object, wherein the at least one verification object is one of: (i) usable for verification without the use of an associated verification engine; (ii) not required to be previously enrolled with user data relating to the at least one verification object; (iii) dynamic; (iv) implicit; (v) able to inherit at least one property from another object; (vi) characterized by multiple inputs; (vii) weighted; and (viii) able to be manipulated. By implicit, it is preferably meant that the object requires no user input, e.g., a caller-id based object. By inheritance, it is preferably meant that one object can inherit a property from another object, e.g., if an object is called color, a new object can be created called car color that inherits properties from the parent object (color).

[0017] In yet another aspect of the invention, the user authentication technique comprises the use of at least one user model and verification means operative to verify a user in accordance with the at least one user model, wherein the at least one user model is one of: (i) representative of one or more user preferences; and (ii) able to be modified for use in subsequent user verification.

[0018] These and other objects, features and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019]FIG. 1 is a block diagram illustrating a client-server architecture of an authentication system for implementing customizable verification using multiple verification objects, according to one embodiment of the invention;

[0020]FIG. 2 is a block diagram illustrating an exemplary computing system environment for implementing customizable verification using multiple verification objects, according to one embodiment of the invention;

[0021]FIG. 3 is a diagram illustrating an exemplary specification of multiple verification objects, according to one embodiment of the invention;

[0022]FIG. 4 is a diagram illustrating an exemplary specification of user models including multiple verification objects, according to one embodiment of the invention;

[0023]FIG. 5 is a diagram illustrating an exemplary specification of customizable verification policies utilizing multiple verification objects for dynamic user authentication, according to one embodiment of the invention;

[0024]FIG. 6 is a state transition diagram illustrating state transition for the example verification policy of FIG. 5; and

[0025]FIG. 7 is a flow diagram illustrating a verification session between a verification client device and a verification server for the example verification policy of FIG. 5.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0026] The following description will illustrate the invention using an exemplary client-server system architecture. It should be understood, however, that the invention is not limited to use with any particular system architecture. The invention is instead more generally applicable to any system architecture in which it is desirable to provide an authentication framework that provides a high degree of flexibility, accuracy, convenience and/or robustness. That is, the techniques of the present invention may be implemented on a single computer system or on multiple computer systems coupled by a suitable network, examples of which will be described below.

[0027] As will be illustratively explained in detail herein, the present invention provides a new programming model that allows full customization of the authentication process to address a wide variety of user-specific, transaction-specific, application-specific constraints and other related requirements, including multiple verification objects.

[0028] The invention further enables a dynamic user authentication process that can respond in real-time to changes in the interaction between the user and the system. The highly flexible architecture permits new verification objects and verification policies to be added at anytime. A common context and associated data structures are included, such that the entire authentication interaction can operate on this shared context.

[0029] In one embodiment, the interaction design is based on authentication policies implemented as a statistical state machine using XML (eXtensible Markup Language). In addition, there is a file that specifies the relevant authentication objects (e.g., questions to be asked, actions to be performed, etc.) and files that contain user profiles (e.g., user selected authentication objects and correct responses, user preferences, etc.) both of which may also be implemented using XML.

[0030] The entire authentication interaction is determined dynamically based on the authentication policy in effect (selected based on user preferences and transaction or application requirements), using operations on the shared context, further utilizing the authentication objects in effect and the user profile of interest.

[0031] Such an approach provides significantly improved authentication capabilities as compared with existing authentication systems, and ensures a very high degree of accuracy, flexibility, convenience and robustness.

[0032] Furthermore, as will be illustratively explained in detail below, the authentication techniques of the present invention utilize the following components: (1) verification objects and verification engines; (2) verification policies and a verification policy manager; and (3) user models.

[0033] Verification objects are objects that can be used for the purpose of verifying the identity of users, such as the user's biometric characteristics (e.g., voiceprint, fingerprint, face scan, iris scan, handwritten signature, keyboard dynamics, etc.), the user's knowledge (e.g., passwords, passphrases, answers to personal questions, etc.), and the user's possessions (e.g., keys, cards, tokens, certificates, cellular telephone or home telephone transmitting caller-id information, personal or handheld computer with client software, user's location, etc.). It is to be understood that the lists of example objects above are not intended to be exhaustive and, further, that the invention is not intended to be limited to any particular objects.

[0034] Verification engines are used to match the verification objects with the representation stored in a user model. Examples of verification engines include a fingerprint recognition system to match the user's fingerprint, a conversational system to evaluate spoken answers to questions such as a voice response system, a conversational system such as a speech or voiceprint recognition system (that may include natural understanding techniques) to extract and recognize a user's spoken utterances (wherein the conversational system may also include a speech synthesis system for generating synthesized questions and prompts), a caller-id recognition system to extract and match the user's telephone number, a badge reader to scan the user's badge or card, a PIN confirmation system to confirm a user's PIN, a face recognition system to extract and match a user's face scan, an iris recognition system to extract and match a user's iris scan, a handwriting recognition system to recognize a user's handwriting, a keyboard dynamic recognizer to match a user's keyboard dynamics, as well as other modality-specific engines discussed herein and/or may otherwise be known. It is to be understood that since these types of engine are well-known, further descriptions of details of such engines are not necessary and therefore are not provided herein. Again, it is to be understood that the list of example engines above is not intended to be exhaustive and, further, that the invention is not intended to be limited to any particular verification engines.

[0035] While verification engines typically perform user verification by comparing user input to the user's model that was created when the user enrolled, the invention is not restricted to verification engines that require user enrollment. Unsupervised verification engines, that do not require the user to enroll, may also be used. When unsupervised verification engines are used, a single user model may be employed, including the user attributes as measured by the verification engines. For example, the following verification engines can be used: acoustic accent recognition, language identification, and face features detection (e.g., color of eyes, glasses detection). In this case, none of the individual verification engines require user enrollment, and one user model is used, stating the user's speech accent spoken, language, color of eyes, and whether he/she wears glasses.

[0036] Thus, the invention realizes that, while individual verification engines can be used to perform simple verification steps that operate in a predefined static manner, a more general framework is necessary when multiple verification objects are used to perform dynamic user authentication, in order to achieve a greater degree of accuracy and flexibility. The present invention provides such an improved authentication framework.

[0037] To accomplish this and other goals, the present invention introduces a notion of verification policies that govern the interaction between the user and the overall system, including the authentication system, and between the various verification engines. Any number of verification policies could be written to satisfy a wide variety of user-specific, transaction-specific or application-specific authentication needs, including needs that change in real-time.

[0038] As will be seen, such verification policies are managed by a verification policy manager which uses operations on a common context shared across all verification objects to achieve maximum programmability of the authentication system.

[0039] In one embodiment of the invention, the verification policies implement a finite state machine, operating on one or more verification objects. Starting from an initial state, transitions occur to other states as the various verification objects are manipulated, including terminal states where the user is accepted or rejected. In some cases, there may be multiple states that grant user acceptance, each with its own security levels (e.g., low security, medium security, high security, etc.) to address the changing security needs of the transaction being processed. The verification policy manager allows for new verification objects to be added at any time, by including the specifications of the new objects in a registry of verification objects, after which verification policies invoking the new verification objects may be utilized.

[0040] User models are typically created when a user enrolls in the system, using the inputs provided by the user (e.g., samples of voice, samples of fingerprint, answers to personal questions, etc.), or acquired through other means (details of past transactions, balance in most recent bill, serial number of a key or badge issued, encryption key contained in a smartcard or a client software, etc.).

[0041] The user models may be updated in real-time when needed, such as when a new bill is issued and the balance changes or when more voice samples are available. An individual user model contains information regarding all verification objects relevant to that user, including any user preferences related to the verification objects (e.g., a user may prefer questions regarding colors rather than numbers). User models also preferably support nontrivial manipulations of the verification objects, such as asking the user to add the first and third digits of his social security number. Again, any of the above-mentioned examples are not intended to limit the invention.

[0042] Given the above general description of some of the principles and features of the present invention, illustrative embodiments of these principles and features will now be given in the context of the figures.

[0043] Referring initially to FIG. 1, a block diagram illustrates a client-server architecture of an authentication system for implementing customizable verification using multiple verification objects, according to one embodiment of the invention. As shown, the authentication system 100 comprises a verification client device 102 and a verification server 104, coupled via a network adapter 106. The verification client 102 has context 108 and application 110 associated therewith. The verification server 104 comprises a verification policy manager 112 and a plurality of verification engines 114-1 through 114-N, where N can be any integer 2, 3, 4 . . . , and represents the number of verification object families or types that the particular implementation of the invention can support. The authentication system 100 further comprises a data manager 116, a verification objects store 118, a verification policies store 120 and a user models store 122. While the data manager 116 and data stores 118, 120 and 122 are shown outside of the verification server box, it is to be understood that they may be implemented on the verification server.

[0044] The verification client device 102 is responsible for interfacing with the user and collecting the inputs from the user, communicating with the verification server 104 through the network adapter 106, and communicating with the application 110. In one embodiment of the invention, the verification client device 102 is also responsible for acquiring and maintaining the context 108.

[0045] In an alternative embodiment, the context 108 may be stored on a central database (not shown), accessible by other components of the system 100. Such an implementation allows for a stateless operation between the verification client device 102 and the verification server 104, such that different servers could be used for different turns in the verification process, thereby providing protection against a particular server going down in the middle of a verification process, and also allowing for improved load balancing of the server resources.

[0046] The context 108 records all relevant variables for the verification process, such as: (1) the user name; (2) the current state in the verification policy that is in effect; (3) the history pertaining to the verification objects that have been invoked and the scores and outcomes associated with the invocations; (4) transaction-specific requirements (e.g., desired level of accuracy, nature of the transaction, etc.); (5) user-specific requirements (e.g., a user having a cold may prefer not to rely on voiceprint match, etc.); and (6) other physical and logical variables (e.g., type of network connection—remote or local, quality of a voice channel, etc.).

[0047] The context 108 may also record other variables that represent verification scores from external verification sources (not shown). For example, a customer entering a bank may have done so after swiping his bank card at the entrance, and that information could be included in the context 108 as an external score and be used for subsequent authentication processes at the counter or at the automated teller machine.

[0048] The variables initially included in the context 108 are system default variables relevant to the verification objects and other known requirements at the time of the initial build. However, as additional verification objects are added to the system 100 or as new requirements are discovered, user-defined variables may be added to the context 108.

[0049] The network adapter 106 enables communication between the client device 102 and the verification server 104. The network adapter 106 implements network transport protocols, such as the standard Transmission Control Protocol (TCP)/Internet Protocol (IP) or the Secure Sockets Layer (SSL) protocol. It is to be understood that in an embodiment where the authentication system 100 is implemented on a single computer system, a network adapter is not required.

[0050] As shown, the verification server 104 comprises a verification policy manager 112 and a set of verification engines 114-1 through 114-N. Each verification engine operates on a given verification object or a family (type) of verification objects. For example, a fingerprint verification engine may operate on a particular fingerprint or different types of fingerprints (e.g., thumbprint, index-fingerprint, etc.). Similarly, a knowledge verification engine may operate on different types of challenge-response questions.

[0051] The flexible architecture allows for easy addition of new verification engines and verification objects. Verification engines to be added could be of a new type or an existing type. For example, a face recognition engine could be added to a verification server that previously comprised voiceprint and fingerprint recognition engines, or a second voiceprint recognition engine (which could be from a different manufacturer, for example) could be added. Similarly, new verification objects could be added to new verification engines or existing verification engines (such as adding a new question to an existing knowledge verification engine).

[0052] The verification policy manager 112 interprets a verification policy for a given user model, and drives the entire authentication process. The policy manager 112 receives the current context 108 from the verification client device 102, operates on the context, incorporates updated status of current verification objects, and returns an updated context to the verification client device 102 along with the specification of the next step to be taken during the verification process.

[0053] In one embodiment of the invention, the verification policy manager 112 is responsible for invoking states in a finite state machine, interpreting the conditions of the state machine and branching to the next state. The verification policy manager 112 is the entity that makes the final accept or reject decision for the authentication process, and in some cases may also make intermediate decisions if the current transaction requires such decisions, provided the verification policy in effect permits it.

[0054] The data manager 116 component controls the external storage resources, including verification objects store 118, verification policies store 120 and user models store 122. These resources may be accessed directly by the verification server 104 (either by the verification policy manager 112 or by the individual verification engines 114-1 through 114-N). In an alternative embodiment, such resources may be accessed by the verification client device 102 and shipped to the verification server 104 through the network adapter 106.

[0055] The application 110 is the application for which user authentication is required prior to granting access. Example applications include banking applications, travel applications and e-mail applications. The application 110 is responsible for providing application-specific and transaction-specific information and requirements. It is to be understood that the invention is not limited to any particular application.

[0056] In one embodiment of the invention, the verification client device 102 communicates with the verification server 104 using an XML message interface. Example functions supported by the interface may comprise the following operations:

[0057] open a communication channel;

[0058] close a verification or enrollment session;

[0059] begin user enrollment and create a user model;

[0060] end user enrollment and close enrollment session;

[0061] start scoring a verification object;

[0062] end scoring a verification object;

[0063] start a verification session;

[0064] continue a verification session to determine the next state within policy or output decision;

[0065] add a new verification object;

[0066] add a new verification policy;

[0067] delete verification policies;

[0068] delete context;

[0069] update a verification object to make changes to an existing verification object;

[0070] update a user model to make changes to an existing user model;

[0071] update a verification policy to make changes to an existing verification policy;

[0072] query a user model to obtain information within a user model;

[0073] query a verification object to obtain information within a verification object;

[0074] query a verification policy to obtain information within a verification policy;

[0075] get a list of active verification objects;

[0076] add a context variable;

[0077] set the current value for a context variable;

[0078] get the current value for a context variable; and

[0079] get a list of all context variable and their current values.

[0080] It is to be understood that the above list of operations is not intended to be exhaustive, and that the invention is not limited to these particular example operations.

[0081] Further, in alternative embodiments, it is to be understood that the components associated with the verification server may themselves communicate with one another over the network adapter 106. Thus, for example, one or more of the verification engines 114 may communicate with the verification policy manager 112 over the network adapter 106. A similar distributed arrangement may exist with respect to the verification policy manager 112 and the data manager 116, and with the data manager 116 and the data stores 118, 120 and 122. Thus, it is to be understood that the interconnectivity of components shown in FIG. 1 is intended to be illustrative and, therefore, other suitable interconnections may be implemented to provide the authentication functionality of the present invention.

[0082] Referring now to FIG. 2, a block diagram illustrates an exemplary computing system environment for implementing customizable verification using multiple verification objects, according to one embodiment of the invention. By way of example, the computing system 200 may represent at least a portion of a distributed computing system wherein a user communicates via a computer system 202 (referred to illustratively as a “client” or client device) with another computer system 204 (referred to illustratively as a “server”) via a network 206. The network may be any suitable network across which the computer systems can communicate, e.g., the Internet or Word Wide Web, local area network, etc. However, the invention is not limited to any particular type of network. In fact, it is to be understood that the computer systems may be directly linked without a network.

[0083] Further, while only two computer systems are shown for the sake of simplicity in FIG. 2, it is to be understood that the network may link a plurality of client devices and a plurality of servers. However, it is also to be appreciated that the techniques of the invention may be implemented on a single computer system wherein, for example, the user interacts directly with the computer system that performs the authentication operations.

[0084] With reference to FIG. 1, it is to be understood that the client device 102 may be implemented via computer system 202, and that the verification server 104 (and its components), the data manager 116 and the respective object, policy and user model stores (118, 120 and 122) may be implemented via the computer system 204. Network adapter 106 would therefore be implemented in accordance with network 206.

[0085] Thus, it is to be understood that FIG. 2 generally illustrates an exemplary architecture for each computer system communicating over the network. As shown, the computer system 202 comprises a processor 208-A, memory 210-A and I/O devices 212-A, all coupled via a computer bus 214-A. Similarly, the computer system 204 comprises a processor 208-B, memory 210-B and I/O devices 212-B, all coupled via a computer bus 214-B.

[0086] It should be understood that the term “processor” as used herein is intended to include one or more processing devices, including a central processing unit (CPU) or other processing circuitry. Also, the term “memory” as used herein is intended to include memory associated with a processor or CPU, such as RAM, ROM, a fixed, persistent memory device (e.g., hard drive), or a removable, persistent memory device (e.g., diskette or CDROM). In addition, the term “I/O devices” as used herein is intended to include one or more input devices (e.g., keyboard, mouse) for inputting data to the processing unit, as well as one or more output devices (e.g., CRT display) for providing results associated with the processing unit. Further, the I/O devices associated with the computer system 202 are understood to include those devices necessary to collect the particular data associated with the verification objects supported by the authentication system, e.g., a microphone to capture voice data for voiceprint recognition and/or answers to questions posed, a speaker to output such questions to the user, a face scanner, an iris scanner, a fingerprint scanner, etc.

[0087] It is also to be understood that the client computer system illustrated in FIG. 2 may comprise a computer system programmed to implement the inventive techniques such as a personal computer, a personal digital assistant, a cellular phone, etc. Likewise, the server computer system illustrated in FIG. 2 may comprise a computer system programmed to implement the inventive techniques such as a personal computer, a microcomputer, a minicomputer, etc. However, the invention is not limited to any particular computer architecture.

[0088] Accordingly, software instructions or code for performing the methodologies of the invention, as described herein, may be stored in one or more of the associated memory devices, e.g., ROM, fixed or removable memory, and, when ready to be utilized, loaded into RAM and executed by the CPU.

[0089] Referring now to FIG. 3, an example is shown of a registry of verification objects. In this particular embodiment, the registry 300 is represented using XML and stored in the verification objects store 118 (FIG. 1).

[0090] The specification contains a description of all registered verification objects, which can be updated as new verification objects are added. The first object (302) in this example is the Date-of-Birth (DOB) object, which is of the type Question-Answer (QA) and the verification engine responsible for operating on this object is the knowledge verification engine. A suggested prompt may also be included to prompt the user for the required response when this object in invoked, but the prompt may be modified or replaced by the verification client, if necessary. The “perplexity” is a quantity that represents the difficulty associated with the verification object and may optionally be used by the verification policy manager in making verification decisions.

[0091] The second object (304) in this example is Caller-ID, which, in the case of a telephony connection, attempts to match the telephone number of the telephone originating the call with the telephone number in the relevant user model. No prompt is specified since this information may be obtained automatically from telephony infrastructure without any explicit input from the user.

[0092] The third object (306) in this example is the Voiceprint object, and in this case no type is specified, since the voiceprint verification engine operates on one type of verification object. Given that voiceprints are a biometric feature that may not be stolen, a high perplexity is specified in this example.

[0093] The fourth and fifth objects (308 and 310) illustrate the hierarchical nature of the specification, whereby the CAR_COLOR object inherits default properties from the parent object COLOR.

[0094] The last two objects (312 and 314) in this example are examples of dynamic verification objects, whereby the intended response changes dynamically, and in this example, the correct responses are obtained from the application, rather than from the user model. The current balance (CUR_BALANCE) object (312) is an application-specific object of the type numeric (APP_NUM) and the last transaction date (LAST_TRANSACTION_DATE) object (314) is an application-specific object of the type string.

[0095] Referring now to FIG. 4, an example is shown of a user model. In this particular embodiment, the user model 400 is represented using XML and stored in the user models store 122 (FIG. 1).

[0096] The user model contains a description of verification objects for which the user has provided enrollment data. The first object (402) is the Caller-ID object, for which this user's correct response is 914-945-3000 in this example. The user's preference for this object may be optionally included and used by the verification policy in selecting objects with higher preference when possible.

[0097] The second and third objects (DOB 404 and COLOR 406) are similar. The fourth object (color of car or CAR_COLOR 408) has two responses in this example, since this user has two cars and either response may be accepted as the correct answer. The fifth object (410) is the voiceprint object, for which model parameters are needed, which may be stored in a file, and the filename is included. The last two objects (CUR_BALANCE 412 and LAST_TRANSACTION_DATE 414) do not have any correct responses included because they are dynamic verification objects, and the current correct responses have to be obtained from the application.

[0098] As mentioned above, in accordance with the present invention, any of the objects can be updated or deleted in real-time, and new objects can be added in real-time.

[0099] Referring now to FIG. 5, an example is shown of a verification policy. In this particular embodiment, the verification policy 500 is implemented as a finite state machine and represented using XML. The corresponding finite state machine diagram is shown in FIG. 6. The verification policy 500 is preferably stored in the verification policies store 120 (FIG. 1).

[0100] Verification policy 500 depicts a simple policy associated with a banking application. More particularly, the policy governs a situation where a user (presumably, a bank client) is trying to gain access to his/her bank account and the authentication system is verifying the identity of the user via multiple verification objects, such as the telephone number of the bank client, the bank client's date of birth, the color of the bank client's car, a voiceprint of the bank client, etc. However, as previously mentioned, the invention is not limited to any particular policy or application. The following illustrative description will make reference to line numbers (e.g., lines 1-53) located on the left-hand side of the verification policy 500.

[0101] First, in FIG. 5, context variables such as “curBalance” (line 4) and “lastTransactionDate” (line 6) are initialized with default values to handle dynamic verification objects such as “CUR_BALANCE” and “LAST_TRANSACTION_DATE”. These variables will subsequently be updated using inputs from the application. The variable “minVoiceprintScore” (line 5) is used to specify the minimum score acceptable for the voiceprint match. The default value for this variable is specified by the verification policy. Different policies may have different default values (e.g., a stricter policy may have a higher minimum score). In an alternative embodiment, the default value may be overwritten by values obtained from either the user model (to account for user-specific requirements) or by the application (to account for transaction-specific or application-specific requirements).

[0102] Next, a set of conditions relevant to the policy are specified, which will be subsequently used to determine state transitions or evaluate verification objects. The expressions used to define the conditions may include context variables, numerical constants and string literals. The expressions may contain operations such as logical AND(&), logical OR (|), equal (=), not equal (!=), less than (<), less than or equal (<=), greater than (>), greater than or equal (>=), multiply(*), divide (/), add (+) and subtract (−)

[0103] For example, the condition “ONE_OK” (line 10), which is a condition used later to determine state transitions, is satisfied if the total number of verification objects invoked so far is one (_curObjectNum =1) and it was a match or there were no mismatches (_curWrongNum=0). Another example of a different kind is the condition “CUR_BALANCE_TEST” (line 15). This condition is used to evaluate the current balance (“CUR BALANCE”) verification object. In this case, a five percent error is allowed, for example, because an approximate answer is satisfactory.

[0104] Following the conditions, a set of states are defined. In this example, there are four states: ACCEPT (line 22), REJECT (line 24), START (line 27) and ACCOUNT (line 40). ACCEPT and REJECT are the terminal states where the final verification decision is made. START is the initial state and contains verification objects “CALLER_ID”, “DOB” and “CAR_COLOR”. By default, verification objects are selected at random, but relative weights may be specified optionally to modify the probability that an object may be selected. Transition to the ACCOUNT state occurs if one of the first two conditions (ONE_OK or TWO_OK_ONE_BAD) is satisfied, and transition to the REJECT state occurs if the third condition (TWO_BAD) is satisfied.

[0105] In the ACCOUNT state, no weights are specified, so all three objects have equal probability of being selected at random. Further, evaluating these objects requires different tests to be used, and these are selected from the previously defined list. Based on the conditions satisfied, transition to either the ACCEPT state or the REJECT state occurs and the corresponding final decision is sent to the verification client device 102 (FIG. 1).

[0106] In an alternative embodiment, intermediate decisions could be made at the intermediate states. For example, a decision to accept the user for low security transactions can be made if certain conditions are satisfied in the START state, and the final decision to accept the user for transactions can be made at the ACCEPT state.

[0107] Referring now to FIG. 6, a state transition diagram illustrates state transition for the example verification policy of FIG. 5. Thus, the state diagram 600 of FIG. 6 illustrates the four states associated with verification policy 500, namely, START (state 602), ACCOUNT (state 604), ACCEPT (state 606) and REJECT (state 608). The arrows between the states represent the conditions for transition between the states, as were described above in the context of verification policy 500 of FIG. 5.

[0108] Referring lastly to FIG. 7, a flow diagram illustrates a verification session between a verification client device and a verification server for the example verification policy of FIG. 5. For instance, such a verification session may take place between verification client device 102 and the verification server 104 of FIG. 1.

[0109] In one embodiment, there are three types of sessions (all of them involve opening and closing sessions):

[0110] (1) an administrative session where operations such as adding/updating/deleting policies, adding/updating/deleting objects, adding context variables, etc., are performed;

[0111] (2) an enrollment session where operations such as creating/updating/deleting user models, etc., are performed; and

[0112] (3) a verification session where operations such as scoring verification objects, continuing a verification session and determining a next state, outputting a verification decision, updating/deleting context, setting/getting a value of a context variable, querying user models/verification objects/verification policies, etc., are performed.

[0113] The administrative session operations may be performed in accordance with an administrator of the authentication system via a client device or directly at the verification server. The enrollment and verification sessions may be performed in accordance with a user via a client device or directly at the verification server.

[0114] The flow chart of FIG. 7 depicts an example operation flow 700 for a verification session, given the verification policy 500 of FIG. 5.

[0115] As shown, in step 702, the client initiates the verification session with the server, stating the name of the policy (SIMPLE_BANK_POLICY) and the usemame (John Doe), with a default context. The server retrieves the policy and the user model referenced.

[0116] The server operates on the policy and the user model, and determines the first verification object to be invoked (DOB, in this example). The server updates the context and sends the request for that object and the context to the client, in step 704.

[0117] The client acquires the response to the invoked verification object (“DOB=Aug. 02, 1975”), and sends the response to a server, in step 706, along with the current context. As mentioned above, in an embodiment utilizing more than one server, the response need not be sent to the initial server, but rather it may be sent to another server in the authentication system. This is due to the stateless client-server nature of communication that may exist in such an embodiment.

[0118] The server (initial or other server) then scores the verification object, updates the context, determines the next state in the policy, and selects and sends the next verification object from the list of available objects (CUR_BALANCE, in this example) along with the updated context to the client, in step 708.

[0119] Since the CUR_BALANCE object is a dynamic object with frequently changing answers, the client updates the relevant context variable with the current value obtained from the application (curBalance =10000), in step 710. In step 712, the server returns acknowledgment to step 710.

[0120] The client acquires the response to the invoked verification object (CUR_BALANCE=10000), and sends the response to a server, in step 714, along with the current context.

[0121] The server then scores the verification object, determines that the policy has been satisfied, and outputs an “ACCEPT” decision, in step 716. The client then ends the verification session.

[0122] It is to be understood that an enrollment session and an administrative session would have respective request-response pairs between the client and the server that are particular to the operations performed in those sessions. It is to be further understood that in an embodiment where the authentication system is implemented on a single computer system, the user interacts directly with the single computer system in performing the operations associated with the particular session.

[0123] Although illustrative embodiments of the present invention have been described herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be made by one skilled in the art without departing from the scope or spirit of the invention. 

What is claimed is:
 1. Apparatus for use in performing user authentication, comprising: at least one processor operative to: (i) obtain user input, wherein at least a portion of the user input is associated with two or more verification objects; and (ii) verify the user based on the two or more verification objects in accordance with at least one verification policy operating on a context shared across the two or more verification objects; and memory, coupled to the at least one processor, for storing at least one of the user input and results associated with the user verification operation.
 2. The apparatus of claim 1, wherein the at least one processor is further operative to perform the user verification operation in accordance with two or more verification processes which are respectively responsive to the two or more verification objects.
 3. The apparatus of claim 2, wherein the two or more verification processes respectively compare the two or more verification objects to at least one user model.
 4. The apparatus of claim 3, wherein the at least one user model is prestored in the memory and accessible by the at least one processor.
 5. The apparatus of claim 4, wherein the at least one user model is shared across the two or more verification objects.
 6. The apparatus of claim 3, wherein the at least one user model is implemented in Extensible Markup Language.
 7. The apparatus claim 1, wherein the at least one verification policy is prestored in the memory and accessible by the at least one processor.
 8. The apparatus of claim 1, wherein the at least one verification policy is implemented in Extensible Markup Language.
 9. The apparatus of claim 1, wherein the context comprises one or more variables associated with the user verification operation.
 10. The apparatus of claim 9, wherein the one or more context variables represent one or more of: (i) a user name; (ii) a current state in the at least one verification policy; (iii) a history pertaining to the two or more verification objects; (iv) application-specific requirements; (v) user-specific requirements; and (vi) physical or logical variables.
 11. The apparatus of claim 1, wherein the two or more verification objects represent at least one of an object type that may be used to verify identity of the user, knowledge of the user, and possessions of the user.
 12. The apparatus of claim 1, wherein the at least one processor is further operative to accept at least one of the addition of, the modification of, and the deletion of at least one of a verification policy, a verification object type, a user model, and a variable associated with the context, for subsequent use in the user verification operation.
 13. A user authentication system, wherein the user authentication system operates in accordance with at least one client device, the system comprising: at least one server coupled to the at least one client device, wherein the at least one server obtains user input from the at least one client device, wherein at least a portion of the user input is associated with two or more verification objects, and further wherein the at least one server verifies the user based on the two or more verification objects in accordance with at least one verification policy operating on a context shared across the two or more verification objects.
 14. The system of claim 13, further wherein the user previously enrolls data, at least a portion of which is used to generate a user model, such that the at least one server utilizes the at least one user model during the user verification operation.
 15. The system of claim 13, wherein the at least one server further comprises two or more verification engines for performing the user verification operation, the two or more verification engines being respectively responsive to the two or more verification objects.
 16. The system of claim 13, wherein the context comprises one or more variables associated with the user verification operation and is maintained at the at least one client device and the at least one server.
 17. The system of claim 16, wherein the one or more context variables represent one or more of: (i) a user name; (ii) a current state in the at least one verification policy; (iii) a history pertaining to the two or more verification objects; (iv) application-specific requirements; (v) user-specific requirements; and (vi) physical or logical variables.
 18. The system of claim 13, wherein the two or more verification objects represent at least one of an object type that may be used to verify identity of the user, knowledge of the user, and possessions of the user.
 19. The system of claim 13, wherein the at least one server is operative to accept at least one of the addition of, the modification of, and the deletion of at least one of a verification policy, a verification object type, a user model, and a variable associated with the context, for subsequent use in the user verification operation.
 20. An automated method of user authentication, the method comprising the steps of: obtaining user input, wherein at least a portion of the user input is associated with two or more verification objects; and verifying the user based on the two or more verification objects in accordance with at least one verification policy operating on a context shared across the two or more verification objects.
 21. The method of claim 20, wherein the user verification step is performed in accordance with two or more verification engines which are respectively responsive to the two or more verification objects.
 22. The method of claim 21, wherein the two or more verification engines respectively compare the two or more verification objects to at least one user model.
 23. The method of claim 22, wherein the at least one user model is shared across the two or more verification objects.
 24. The method of claim 22, wherein the at least one user model is previously generated based on data obtained in accordance with a user enrollment session.
 25. The method of claim 20, wherein the context comprises one or more variables associated with the user verification step.
 26. The method of claim 25, wherein the one or more context variables represent one or more of: (i) a user name; (ii) a current state in the at least one verification policy; (iii) a history pertaining to the two or more verification objects; (iv) application-specific requirements; (v) user-specific requirements; and (vi) physical or logical variables.
 27. The method of claim 20, wherein the two or more verification objects represent at least one of an object type that may be used to verify identity of the user, knowledge of the user, and possessions of the user.
 28. The method of claim 20, further comprising the step of accepting at least one of the addition of, the modification of, and the deletion of at least one of a verification policy, a verification object type, a user model, and a variable associated with the context, for subsequent use in the user verification operation.
 29. An article of manufacture for use in user authentication, comprising a machine readable medium containing one or more programs which when executed implement the steps of: obtaining user input, wherein at least a portion of the user input is associated with two or more verification objects; and verifying the user based on the two or more verification objects in accordance with at least one verification policy operating on a context shared across the two or more verification objects.
 30. The article of claim 29, wherein the user verification step is performed in accordance with two or more verification engines which are respectively responsive to the two or more verification objects.
 31. The article of claim 30, wherein the two or more verification engines respectively compare the two or more verification objects to at least one user model.
 32. The article of claim 29, wherein the at least one user model is shared across the two or more verification objects.
 33. The article of claim 32, wherein the at least one user model is previously generated based on data obtained in accordance with a user enrollment session.
 34. The article of claim 29, wherein the context comprises one or more variables associated with the user verification step.
 35. The article of claim 34, wherein the one or more context variables represent one or more of: (i) a user name; (ii) a current state in the at least one verification policy; (iii) a history pertaining to the two or more verification objects; (iv) application-specific requirements; (v) user-specific requirements; and (vi) physical or logical variables.
 36. The article of claim 29, wherein the two or more verification objects represent at least one of an object type that may be used to verify identity of the user, knowledge of the user, and possessions of the user.
 37. The article of claim 29, further comprising the step of accepting at least one of the addition of, the modification of, and the deletion of at least one of a verification policy, a verification object type, a user model, and a variable associated with the context, for subsequent use in the user verification operation.
 38. An authentication system, comprising: a verification manager; and verification means coupled to the verification manager; wherein the verification manager is operative to control the steps of: (i) verifying a user in accordance with the verification means; and (ii) customizing the user verification means for subsequent user verification.
 39. The system of claim 38, wherein the user verification means customizing operation comprises at least one of adding, modifying, and deleting at least one of a verification policy, a verification object type, a user model, and a variable associated with a verification context.
 40. The system of claim 38, wherein the user verification means customizing operation further comprises customizing the user verification means to enable handling of at least one of a user-specific constraint, an application-specific constraint, and a transaction-specific constraint.
 41. An authentication system, comprising: a verification manager; and two or more verification engines coupled to the verification manager; wherein the verification manager is operative to control the steps of: (i) obtaining user input, wherein at least a portion of the user input is associated with two or more verification objects; and (ii) verifying the user, using the two or more verification engines, based on the two or more verification objects in accordance with at least one verification policy operating on a context shared across the two or more verification objects.
 42. The system of claim 41, wherein the verification policy manager is further operative to control at least one of the addition of, the modification of, and the deletion of at least one new verification engine.
 43. The system of claim 42, wherein the at least one new verification engine is responsive to one of an existing verification object and a new verification object.
 44. The system of claim 41, wherein the verification manager and at least one of the two or more verification engines are coupled via a network.
 45. The system of claim 41, wherein the verification manager and the two or more verification engines are associated with a verification server and further wherein the authentication system comprises a client device in communication with the verification server.
 46. The system of claim 45, wherein the context is storable at a central location accessible by at least the client device and the verification server such that the client device and the verification server are able to participate in stateless communication.
 47. The system of claim 41, wherein the authentication system further comprises data storage means for storing at least one of the verification policy, a specification of the two or more verification policies, and a user model used to perform user verification.
 48. The system of claim 47, wherein the data storage means is accessible to one of the verification manager, the two or more verification engines, and a client device coupled to the verification manager.
 49. A user authentication system, wherein the user authentication system operates in accordance with at least one client device, the system comprising: at least one server coupled to the at least one client, wherein the at least one server obtains user input from the at least one client device and verifies the user based on at least a portion of the user input, and further wherein a communication interface between the at least one client device and the at least one server is implemented in accordance with Extensible Markup Language.
 50. The system of claim 49, wherein the communication interface between the at least one client device and the at least one server supports at least one of a verification session, an enrollment session, and an administrative session.
 51. An authentication system, comprising: at least one verification policy; and verification means operative to verify a user in accordance with the at least one verification policy, wherein the at least one verification policy is implementable in accordance with the verification means as a state machine.
 52. The system of claim 51, wherein the state machine comprises at least one of a terminal state and an intermediate state in which a decision is output.
 53. The system of claim 51, wherein the at least one verification policy is dynamic.
 54. The system of claim 51, wherein the at least one verification policy is based on one or more conditions which are capable of branching to one or more different states.
 55. An authentication system, comprising: at least one verification object; and verification means operative to verify a user in accordance with the at least one verification object, wherein the at least one verification object is at least one of: (i) usable for verification without the use of an associated verification engine; (ii) not required to be previously enrolled with user data relating to the at least one verification object; (iii) dynamic; (iv) implicit; (v) able to inherit at least one property from another object; (vi) characterized by multiple inputs; (vii) weighted; and (viii) able to be manipulated.
 56. The system of claim 55, wherein the verification object has a perplexity value associated therewith.
 57. The system of claim 56, wherein a verification policy associated with the verification means uses the perplexity value.
 58. An authentication system, comprising: at least one user model; and verification means operative to verify a user in accordance with the at least one user model, wherein the at least one user model is at least one of: (i) representative of one or more user preferences; and (ii) able to be modified for use in subsequent user verification.
 59. An authentication system, comprising: a verification manager; and one or more verification engines coupled to the verification manager; wherein the verification manager is operative to control the steps of: (i) obtaining user input, wherein at least a portion of the user input is associated with one or more verification objects; (ii) obtaining data associated with an external source; and (iii) verifying the user, using the one or more verification engines based on the one or more verification objects and using the external source data, in accordance with at least one verification policy operating on a context shared across the one or more verification objects and the external source data.
 60. An authentication system, comprising: at least one verification policy; and verification means operative to verify a user in accordance with the at least one verification policy, wherein the at least one verification policy is based on at least one verification object, one or more context variables and external source data.
 61. An automated method of authenticating a user, the method comprising the steps of: verifying the user in accordance with the verification means; and customizing the user verification means for subsequent user verification.
 62. An automated method of authenticating a user, the method comprising the steps of: obtaining user input; and verifying the user based on at least a portion of the user input in accordance with at least one verification policy, wherein the at least one verification policy is implementable as a state machine.
 63. The method of claim 62, wherein the verifying step further comprises outputting at least one of an intermediate decision and a terminal decision.
 64. An automated method of authenticating a user, the method comprising the steps of: obtaining user input, wherein at least a portion of the user input is associated with at least one verification object; and verifying the user in accordance with the at least one verification object, wherein the at least one verification object is at least one of: (i) usable for verification without the use of an associated verification engine; (ii) not required to be previously enrolled with user data relating to the at least one verification object; (iii) dynamic; (iv) implicit; (v) able to inherit at least one property from another object; (vi) characterized by multiple inputs; (vii) weighted; and (viii) able to be manipulated.
 65. An automated method of authenticating a user, the method comprising the steps of: obtaining at least one user model; and verifying a user in accordance with the at least one user model, wherein the at least one user model is at least one of: (i) representative of one or more user preferences; and (ii) able to be modified for use in subsequent user verification.
 66. An automated method of authenticating a user, the method comprising the steps of: obtaining at least one verification policy; and verifying a user in accordance with the at least one verification policy, wherein the at least one verification policy is based on at least one verification object, one or more context variables and external source data. 